For historical reference, this PR fixes @PreDestroy interceptors/callbacks being invoked twice for @Dependent beans, when the dependent bean was created through BeanManager.getReference() and is destroyed through Bean.destroy().

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

... when the dependent bean was created through BeanManager.getReference() and is destroyed through Bean.destroy().

Just my favourite way of creating and destroying beans :)

I am a bite late but LGTM and thanks for fixing this!

@mkouba is this something that we want backported to 3.0.2.Final?

@mkouba is this something that we want backported to 3.0.2.Final?

I don't think it's necessary because the problem was only spotted in the TCK runner. @Ladicek @manovotn WDYT?

Agree, I don't think we need to backport this.

+1, no need to port this.